Skip to content

Add and correct 26.1 protocol and registry mappings#1169

Closed
Mikulasz12 wants to merge 3 commits intoPrismarineJS:masterfrom
Mikulasz12:feature/26.1-compat
Closed

Add and correct 26.1 protocol and registry mappings#1169
Mikulasz12 wants to merge 3 commits intoPrismarineJS:masterfrom
Mikulasz12:feature/26.1-compat

Conversation

@Mikulasz12
Copy link
Copy Markdown

Summary

This PR brings the existing 26.1 data branch onto master and adds the follow-up fixes needed to make 26.1 decode.

What changed

  • merges the existing pc_26_1 data work into master
  • fixes the 26.1 dataPaths wiring
  • adds corrected 26.1 data for:
    • blocks
    • items
    • blockCollisionShapes
  • updates the 26.1 protocol mappings

Why

The initial 26.1 data branch was enough to get protocol and version support in place, but some 26.1 registry data had drifted.

In practice that meant clients could connect, but some ids decoded incorrectly. For example:

  • iron_bars came through as copper_bars
  • soul_lantern came through as copper_lantern
  • blockAt() read a placed soul_lantern as crimson_pressure_plate

Verification

Tested with a Mineflayer bot using version: "26.1" against a vanilla server.

Checked that:

  • inventory items decoded correctly
  • placed blocks read back correctly

Examples verified:

  • iron_bars
  • soul_lantern
  • oak_planks

@Mikulasz12 Mikulasz12 force-pushed the feature/26.1-compat branch from 763d515 to 2dbffbe Compare March 31, 2026 22:06
@Mikulasz12 Mikulasz12 force-pushed the feature/26.1-compat branch from 2dbffbe to ed54b1d Compare March 31, 2026 22:16
@extremeheat
Copy link
Copy Markdown
Member

Please open this PR against the pc_26_1 branch in #1160

@extremeheat
Copy link
Copy Markdown
Member

Data like blockCollisionShapes is supposed to come from minecraft-data-generator, should not need to manually modify them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants